chore: bump deps #276
chore: bump deps #276
Conversation
Updated dependencies Signed-off-by: Serge Logvinov <serge.logvinov@sinextra.dev>
WalkthroughThe pull request performs routine maintenance updates across three files. The Go toolchain is bumped to version 1.25.6 in both the Dockerfile base image and the go.mod configuration. The golangci-lint GitHub Action in the CI workflow is updated from v2.6.2 to v2.8.0. Additionally, nine Go dependencies receive patch or minor version updates, including packages for Proxmox, Prometheus, and standard library modules (crypto, net, sys, term, text, exp) plus Kubernetes utilities. No code logic, exports, or API changes are present. Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In @.github/workflows/build-test.yaml:
- Around line 31-35: The workflow update sets the Lint step to use golangci-lint
version v2.8.0 (see Lint step and version: v2.8.0 in
.github/workflows/build-test.yaml); run a CI/test pass locally or in a branch
with that workflow to surface any new linter failures, and if failures occur
update .golangci.yml to explicitly disable or configure the new checks
(godoc-lint's require-stdlib-doclink, gosec G116, modernize's
stringscut/unsafefuncs, unqueryvet options) or adjust rules/severity, or
temporarily pin the workflow to the prior working golangci-lint version until
the config is updated; iterate until the pipeline is green.
| - name: Lint | ||
| uses: golangci/golangci-lint-action@v9 | ||
| with: | ||
| version: v2.6.2 | ||
| version: v2.8.0 | ||
| args: --timeout=5m --config=.golangci.yml |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
golangci-lint v2.8.0 release notes breaking changes
💡 Result:
golangci-lint v2.8.0 (released January 7, 2026) does not list any explicit “breaking changes” in its official release notes/changelog—no CLI/config removals or incompatible defaults are called out for this version. (golangci-lint.run)
The changes most likely to impact CI results (i.e., “practically breaking” due to new/changed findings) are linter updates: (golangci-lint.run)
- New checks/rules added by bundled linters
godoc-lint: new rulerequire-stdlib-doclink(golangci-lint.run)gosec: new ruleG116(golangci-lint.run)modernize: new analyzersstringscut,unsafefuncs(golangci-lint.run)
- New linter options that could change behavior if you configure them
unqueryvet: adds multiple new options (e.g.,check-subqueries,sql-builders, etc.) (golangci-lint.run)
- Output/message changes
prealloc: “message changes” (can affect baselines/golden files) (golangci-lint.run)
Citations:
- 1: https://golangci-lint.run/docs/product/changelog/
- 2: https://golangci-lint.run/docs/product/changelog/
- 3: https://golangci-lint.run/docs/product/changelog/
- 4: https://golangci-lint.run/docs/product/changelog/
- 5: https://golangci-lint.run/docs/product/changelog/
- 6: https://golangci-lint.run/docs/product/changelog/
- 7: https://golangci-lint.run/docs/product/changelog/
🌐 Web query:
golangci-lint v2.8.0 Go 1.25 support compatibility
💡 Result:
- Yes,
golangci-lint v2.8.0is compatible with Go 1.25, as long as thegolangci-lintbinary you run was built with Go 1.25 (or newer).golangci-lintgenerally supports analyzing Go code for versions ≤ the Go version used to compilegolangci-lint. [2][3] - Go 1.25 was released August 12, 2025, and
golangci-lintmaintainers note that official binaries are built with Go 1.25 (so the official release artifacts should work with Go 1.25 projects). [3][4] v2.8.0itself was released 2026-01-07. [1]- Gotcha: if you install via a package manager (Homebrew/Nix/etc.) that rebuilds
golangci-lintwith an older Go toolchain, the resulting binary may not properly support Go 1.25; in that case use the official binaries or build it yourself with Go 1.25. [3]
Sources: golangci-lint v2.8.0 changelog [1], support policy FAQ [2], Go 1.25 support discussion (golangci-lint) [3], Go 1.25 release announcement [4].
🌐 Web query:
golangci-lint-action v9 golangci-lint version 2.8.0 compatibility
💡 Result:
Yes—golangci/golangci-lint-action@v9 is compatible with golangci-lint v2.8.0.
- The action’s documented requirement for golangci-lint v2 is “>= v2.1.0” (stated for v8; v9’s change is the Node.js runtime bump to node24, not a new golangci-lint minimum), so v2.8.0 satisfies it. [1], [2]
golangci-lint v2.8.0was released 2026-01-07. [3]
If you’re pinning it, use:
- uses: golangci/golangci-lint-action@v9
with:
version: v2.8.0Sources: [1] [2] [3]
Review v2.8.0 for new linter checks that could fail in CI.
While v2.8.0 introduces no config-breaking changes and fully supports Go 1.25, it adds new linter rules (godoc-lint's require-stdlib-doclink, gosec's G116, modernize's stringscut/unsafefuncs, and unqueryvet options) and changes prealloc's output messages. Run a test pass with this version to ensure these new checks don't cause unexpected lint failures.
🤖 Prompt for AI Agents
In @.github/workflows/build-test.yaml around lines 31 - 35, The workflow update
sets the Lint step to use golangci-lint version v2.8.0 (see Lint step and
version: v2.8.0 in .github/workflows/build-test.yaml); run a CI/test pass
locally or in a branch with that workflow to surface any new linter failures,
and if failures occur update .golangci.yml to explicitly disable or configure
the new checks (godoc-lint's require-stdlib-doclink, gosec G116, modernize's
stringscut/unsafefuncs, unqueryvet options) or adjust rules/severity, or
temporarily pin the workflow to the prior working golangci-lint version until
the config is updated; iterate until the pipeline is green.
Updated dependencies
Pull Request
What? (description)
Why? (reasoning)
Acceptance
Please use the following checklist:
make lint)make unit)Summary by CodeRabbit
Chores
✏️ Tip: You can customize this high-level summary in your review settings.